			Readme for arcopy utility

Notes: 
1. tirpc32.dll is required for the arcopy utility to run on NT, this dll
is available from <Rem-Ins-Dir>\bin directory.
2. You should use an AR Administrator user to ensure that data from all fields 
is exported and imported because this user has full access.


NAME
     arcopy - copy data into or out of an AR System database

SYNOPSIS
     arcopy [ Source [ Destination [ User [ Password ] ] ] ]
            [ -id { new | old | fixup } ]

DESCRIPTION
     arcopy is used to copy the database records from an AR  Sys-
     tem  server to a file or from a file to an AR System server.
     Unlike the import/export facilities of the  aradmin  program
     which work with structure definitions, this program operates
     on the database records.  Before the program  can  be  used,
     the  respective schema definitions must already exist on the
     target server.

OPTIONS
     The options to arcopy are positional.  The first  four  must
     be  supplied  (or  they  are  prompted  for) while the final
     option is optional.

     If any of the positional arguments are omitted, the  program
     will prompt you for the values for the remaining parameters.
     For example, if you omit, the password, you will be prompted
     for  it.   If  you  omit  the User and Password, you will be
     prompted for both.  To be prompted for all parameters,  sim-
     ply enter arcopy without any parameters.

     Source
          The source of the database to be copied.  This  can  be
          either  a data file or an AR System server.  If it con-
          tains a trailing ':' then it is assumed to be an
          AR  System server.  Otherwise, it specifies the name of
          a file from which to read data records.

          To specify an AR System server, give the  name  of  the
          system followed by a colon.  For example, remedy: would
          specify the AR System  server  running  on  the  system
          remedy.   In  this  case,  all schemas in the remedy AR
          System server will be copied.

          If you wish to copy specific schemas, add the names  of
          the  schemas  following  the colon.  Separate more than
          one schema by commas (no spaces).  Since  schema  names
          may  contain  spaces and special characters, which is a
          problem for UNIX  utilities,  those  containing  spaces
          and/or  special characters must be surrounded by double
          quotes.    For   example,    remedy:User,Group,"Trouble
          Ticket"  will  select  three schemas from the remedy AR
          System server.

     Destination


          The destination for the copy  operation.   The  general
          format  and  operation  of  this  option is the same as
          Source with one addition.

          The addition involves merging data  from  one  database
          into  a  database with a different name.  If the schema
          on the target database has a different  name  than  the
          source, you must enter the schema name using the syntax
          "target-schema-name=source-schema-name"   to   identify
          which  schema is the target for the operation and which
          schema is the source.

          The program will only support copying from a server  to
          a  file  or  from  a file to a server.  You cannot copy
          between two files or between two servers (without going
          out to a file as an intermediate step).

     User The User for AR System server login.  All of the opera-
          tions performed by arcopy require credentials (User and
          Password) on each operation.

     Password
          The password for the User.  The system will prompt  for
          the  password if one is not specified.  The prompt does
          not echo so if you want to hide the password from other
          users, omit it and supply the pasword when prompted.

     -id  An  optional  parameter  identifying  how  to  map  the
          entryId field of the schema.  If set, it must be one of
          the following values:
             new  - Create a new entryId  for  all  the  entries,
          ignoring the old ID
             old   - Use the old entryId  for  all  entries.   If
          there  is  a  conflict  with  an existing ID, return an
          error message and do not merge the entry.  This is  the
          default.
             fixup - Use the old entryId  for  all  entries.   If
          there  is  a  conflict  with  an  existing ID, create a
          unique ID for the entry and create the entry.

ENVIRONMENT
     ARRPC
          Defines the specific RPC  socket  to  communicate  with
          during  the run of the program.  If there is no AR Sys-
          tem server running on the identified socket,  an  error
          will be returned and the program will not run.  In gen-
          eral, this variable is not used.

EXAMPLES
     arcopy remedy:TroubleTicket TT.data "Demo" ""

     Export the contents of the TroubleTicket  schema  on  server
     remedy into a file named TT.data.

FILES
     /etc/ar

SEE ALSO
     aradmin(1), arimport(1), arserverd(1), aruser(1)

WARNINGS
     The entries that can be imported or exported have some  lim-
     its.   The maximum size of a single diary or long text entry
     is 64K bytes.  The maximum size of an entire entry,  includ-
     ing data in all fields, is 100K.

     This program has been superceeded by arimport for  importing
     and  aruser  for exporting.  You should convert to using the
     arimport procedure for your data  import  needs  and  aruser
     using reporting for your data export needs.
